Require non-null user and container in UserSchemas#6413
Conversation
|
BVTs, etc. all green except for known, unrelated failures (see above). Daily postgres all green except for known, unrelated failures: https://teamcity.labkey.org/buildConfiguration/LabkeyTrunk_DailyPostgres_2/3407932 |
labkey-jeckels
left a comment
There was a problem hiding this comment.
Can we also annotate the variables and getters as @NotNull?
I think I have the ability to do that. Of course, there are 140 user schemas, so hard to know where to stop. I chose to annotate 6 - 7 "top-level" user schemas. |
I was just thinking within this class, but nice to begin to propagate out to subclasses |
Rationale
A
UserSchemawith anullUserorContainerseems less useful. Throw if either are null at construction time.Related Pull Requests